Forwarded: not yet.
Bug-Debian: https://bugs.debian.org/1027168
onetbb currently FTBFS on sh4 because the source code assumes that the target
FPU supports all four rounding modes (FE_TONEAREST, FE_DOWNWARD, FE_UPWARD and
FE_TOWARDZERO) which is not the case on sh4 which supports FE_TONEAREST and
FE_TOWARDZERO only [1].
The attached patch fixes these assumptions for sh4 and makes the code build. I
have already patched and uploaded the package to the unreleased distribution
so that the mold linker can build on sh4 as well.
I will forward the patch later after reformating it.
Forwarded: not yet.
Bug-Debian: https://bugs.debian.org/1027168
onetbb currently FTBFS on sh4 because the source code assumes that the target
FPU supports all four rounding modes (FE_TONEAREST, FE_DOWNWARD, FE_UPWARD and
FE_TOWARDZERO) which is not the case on sh4 which supports FE_TONEAREST and
FE_TOWARDZERO only [1].
The attached patch fixes these assumptions for sh4 and makes the code build. I
have already patched and uploaded the package to the unreleased distribution
so that the mold linker can build on sh4 as well.
I will forward the patch later after reformating it.
Forwarded: not yet.
BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027168
onetbb currently FTBFS on sh4 because the source code assumes that the target
FPU supports all four rounding modes (FE_TONEAREST, FE_DOWNWARD, FE_UPWARD and
FE_TOWARDZERO) which is not the case on sh4 which supports FE_TONEAREST and
FE_TOWARDZERO only [1].
The attached patch fixes these assumptions for sh4 and makes the code build. I
have already patched and uploaded the package to the unreleased distribution
so that the mold linker can build on sh4 as well.
I will forward the patch later after reformating it.
===================================================================
Forwarded: not yet.
BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027168
onetbb currently FTBFS on sh4 because the source code assumes that the target
FPU supports all four rounding modes (FE_TONEAREST, FE_DOWNWARD, FE_UPWARD and
FE_TOWARDZERO) which is not the case on sh4 which supports FE_TONEAREST and
FE_TOWARDZERO only [1].
The attached patch fixes these assumptions for sh4 and makes the code build. I
have already patched and uploaded the package to the unreleased distribution
so that the mold linker can build on sh4 as well.
I will forward the patch later after reformating it.
===================================================================
Mo Zhou [Sat, 22 Feb 2025 18:51:55 +0000 (13:51 -0500)]
onetbb (2022.0.0-2) unstable; urgency=medium
* d/rules: Clean the html directory as well. (Closes: #1045631)
* d/control: Update the homepage URL.
* Bump Standards-Version to 4.7.0 (no change needed).
* Apply wrap-and-sort.
Forwarded: not yet.
BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027168
onetbb currently FTBFS on sh4 because the source code assumes that the target
FPU supports all four rounding modes (FE_TONEAREST, FE_DOWNWARD, FE_UPWARD and
FE_TOWARDZERO) which is not the case on sh4 which supports FE_TONEAREST and
FE_TOWARDZERO only [1].
The attached patch fixes these assumptions for sh4 and makes the code build. I
have already patched and uploaded the package to the unreleased distribution
so that the mold linker can build on sh4 as well.
I will forward the patch later after reformating it.
===================================================================
Forwarded: not yet.
BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027168
onetbb currently FTBFS on sh4 because the source code assumes that the target
FPU supports all four rounding modes (FE_TONEAREST, FE_DOWNWARD, FE_UPWARD and
FE_TOWARDZERO) which is not the case on sh4 which supports FE_TONEAREST and
FE_TOWARDZERO only [1].
The attached patch fixes these assumptions for sh4 and makes the code build. I
have already patched and uploaded the package to the unreleased distribution
so that the mold linker can build on sh4 as well.
I will forward the patch later after reformating it.
Avoid build problem on armel caused by strange compiler.
Add indirection and a result test which seem to confuse GCC 13 less
than the original statements.
Fixes build problem:
In file included from /usr/include/c++/13/atomic:41,
from /<<PKGBUILDDIR>>/test/common/doctest.h:2990,
from /<<PKGBUILDDIR>>/test/common/test.h:32,
from /<<PKGBUILDDIR>>/test/tbb/test_concurrent_monitor.cpp:26:
In member function ‘void std::__atomic_base<_IntTp>::store(__int_type, std::memory_order) [with _ITp = bool]’,
inlined from ‘void std::atomic<bool>::store(bool, std::memory_order)’ at /usr/include/c++/13/atomic:104:20,
inlined from ‘void tbb::detail::r1::concurrent_monitor_base<Context>::notify_one_relaxed() [with Context = unsigned int]’ at /<<PKGBUILDDIR>>/test/tbb/../../src/tbb/concurrent_monitor.h:293:53,
inlined from ‘void tbb::detail::r1::concurrent_monitor_base<Context>::notify_one() [with Context = unsigned int]’ at /<<PKGBUILDDIR>>/test/tbb/../../src/tbb/concurrent_monitor.h:276:27,
inlined from ‘void DOCTEST_ANON_FUNC_35()’ at /<<PKGBUILDDIR>>/test/tbb/test_concurrent_monitor.cpp:87:44:
/usr/include/c++/13/bits/atomic_base.h:481:25: error: ‘void __atomic_store_1(volatile void*, unsigned char, int)’ writing 1 byte into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
481 | __atomic_store_n(&_M_i, __i, int(__m));
| ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
Author: Petter Reinholdtsen <pere@debian.org>
Forwarded: no
Bug-Debian: https://bugs.debian.org/1042009
Last-Update: 2023-07-31
Avoid build problem on armel caused by strange compiler.
Add indirection and a result test which seem to confuse GCC 13 less
than the original statements.
Fixes build problem:
In file included from /usr/include/c++/13/atomic:41,
from /<<PKGBUILDDIR>>/test/common/doctest.h:2990,
from /<<PKGBUILDDIR>>/test/common/test.h:32,
from /<<PKGBUILDDIR>>/test/tbb/test_concurrent_monitor.cpp:26:
In member function ‘void std::__atomic_base<_IntTp>::store(__int_type, std::memory_order) [with _ITp = bool]’,
inlined from ‘void std::atomic<bool>::store(bool, std::memory_order)’ at /usr/include/c++/13/atomic:104:20,
inlined from ‘void tbb::detail::r1::concurrent_monitor_base<Context>::notify_one_relaxed() [with Context = unsigned int]’ at /<<PKGBUILDDIR>>/test/tbb/../../src/tbb/concurrent_monitor.h:293:53,
inlined from ‘void tbb::detail::r1::concurrent_monitor_base<Context>::notify_one() [with Context = unsigned int]’ at /<<PKGBUILDDIR>>/test/tbb/../../src/tbb/concurrent_monitor.h:276:27,
inlined from ‘void DOCTEST_ANON_FUNC_35()’ at /<<PKGBUILDDIR>>/test/tbb/test_concurrent_monitor.cpp:87:44:
/usr/include/c++/13/bits/atomic_base.h:481:25: error: ‘void __atomic_store_1(volatile void*, unsigned char, int)’ writing 1 byte into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
481 | __atomic_store_n(&_M_i, __i, int(__m));
| ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
Author: Petter Reinholdtsen <pere@debian.org>
Forwarded: no
Bug-Debian: https://bugs.debian.org/1042009
Last-Update: 2023-07-31
projects / onetbb.git / log